Course: Core Java Training
Topic: Understanding Java Editions: Java SE, Jakarta EE, and Java ME
Course Link: Core Java Training Course
Demo Link: Register for a Course Demo
Website: JustAcademy Official Website
Java is a widely used programming language for developing desktop applications, web applications, enterprise systems, mobile-related software, and network services. To support different application requirements, Java technologies have been organized into different editions and platform specifications.
The three editions and platform families commonly introduced to Java learners are:
These platforms serve different purposes. Java SE is the foundation for learning Java programming, Jakarta EE extends Java technology for enterprise application development, and Java ME addresses selected embedded and constrained-device environments.
Important terminology: Jakarta EE is the modern continuation of Java EE under the Eclipse Foundation. Java EE was transferred from Oracle to the Eclipse Foundation and renamed Jakarta EE. Java ME remains a separate platform family.
After studying this topic, you will be able to:
Java SE stands for Java Platform, Standard Edition. It is the core Java platform used to develop general-purpose applications. It provides the programming language, standard APIs, development tools, and runtime environment needed for most foundational Java programming tasks.
Java SE is the starting point for learning Core Java because it covers the language features and libraries that developers use in many different types of Java applications.
| Component | Description |
|---|---|
| Java Language | Defines Java syntax, data types, classes, interfaces, and language rules. |
| JVM | Executes Java bytecode and manages runtime operations. |
| Java Standard APIs | Provide reusable functionality for collections, input/output, networking, dates, and other common tasks. |
| JDK | Provides development tools and the components required to compile and develop Java applications. |
| JDBC | Provides standard interfaces for connecting Java applications to databases. |
The following program demonstrates a basic Java SE application using the standard Java language and console output functionality.
public class JavaSEExample {
public static void main(String[] args) {
String name = "Java SE";
int year = 2026;
System.out.println("Platform: " + name);
System.out.println("Year: " + year);
}
}Output:
Platform: Java SE
Year: 2026This program uses a class, a main method, variables, the String type, an integer, and System.out.println(). These are foundational Java concepts used across many Java development environments.
Java SE is used in a wide variety of software development tasks, including:
Jakarta EE stands for Jakarta Enterprise Edition. It is a collection of enterprise Java specifications and APIs designed to simplify the development of web applications, business applications, RESTful services, and distributed enterprise systems.
Jakarta EE builds on the Java platform and provides standardized services that enterprise applications commonly need. Instead of implementing every infrastructure feature from scratch, developers can use APIs for web requests, persistence, transactions, dependency injection, security, and messaging. Compatible application servers or runtimes provide implementations of these specifications. Read the Jakarta EE overview.
Jakarta EE continues the evolution of Java EE, which was originally developed under Oracle's stewardship. The enterprise platform moved to the Eclipse Foundation, where its specifications are maintained through an open, community-driven process.
The name changed from Java EE to Jakarta EE. Beginning with Jakarta EE 9, enterprise APIs transitioned from the javax.* namespace to the jakarta.* namespace for the specifications that underwent this change.
This distinction is important when maintaining older Java EE applications or migrating them to newer Jakarta EE versions because package names, dependencies, and compatible server versions may need to be updated.
| Technology | Purpose |
|---|---|
| Jakarta Servlet | Processes HTTP requests and responses on the server. |
| Jakarta REST | Develops RESTful web services and APIs. |
| Jakarta Persistence | Maps Java objects to relational database records. |
| Jakarta CDI | Provides dependency injection and contextual lifecycle management. |
| Jakarta Faces | Supports server-side user interface development. |
| Jakarta Validation | Defines validation rules for application data. |
| Jakarta Messaging | Supports message-based communication between application components. |
| Jakarta Transactions | Provides transaction management APIs. |
| Jakarta Security | Provides standard security APIs for enterprise applications. |
The following example illustrates a basic REST endpoint using Jakarta REST. It returns a simple text response when the specified resource is requested.
import jakarta.ws.rs.GET;
import jakarta.ws.rs.Path;
import jakarta.ws.rs.Produces;
import jakarta.ws.rs.core.MediaType;
@Path("/hello")
public class HelloResource {
@GET
@Produces(MediaType.TEXT_PLAIN)
public String sayHello() {
return "Hello from Jakarta EE!";
}
}Explanation:
@Path("/hello") defines the resource path.@GET indicates that the method handles HTTP GET requests.@Produces(MediaType.TEXT_PLAIN) specifies a plain-text response.sayHello() returns the response body.When deployed to a compatible Jakarta EE runtime with REST application configuration, the endpoint can respond at a URL ending in /hello, with the complete path depending on the application's deployment context.
Important: The example uses the modern jakarta.ws.rs package namespace. Older Java EE applications and Jakarta EE 8 applications use different package conventions, so code and dependencies must match the target platform.
Java ME stands for Java Platform, Micro Edition. It is a Java technology platform family intended for selected embedded, mobile, and resource-constrained devices.
Java ME specifications and runtimes are designed for environments where memory, processing power, storage, connectivity, or energy consumption may be more limited than on general-purpose computers and servers. Depending on the implementation, Java ME can support embedded devices, industrial equipment, gateways, and certain specialized device categories.
Java ME is not the same thing as modern Android development. Android has its own application platform and runtime environment, and Android applications commonly use Kotlin or Java with Android-specific APIs.
Historically, Java ME used configurations and profiles to provide a suitable set of APIs for different device categories.
For example, the Connected Limited Device Configuration (CLDC) was designed for certain resource-constrained devices. Mobile Information Device Profile (MIDP) added APIs for supported mobile devices. These are important historical concepts, although current Java ME products and embedded deployments vary in their supported specifications.
The following example demonstrates the familiar Java language structure that may appear in a Java ME environment. It illustrates basic language concepts rather than a device-specific API.
public class DeviceMessage {
public static void main(String[] args) {
System.out.println("Java on a supported device");
}
}Note: This example uses standard Java syntax, but it does not demonstrate a complete Java ME application lifecycle. Actual Java ME applications must follow the entry-point, packaging, and runtime requirements of their target profile or implementation.
| Comparison Factor | Java SE | Jakarta EE | Java ME |
|---|---|---|---|
| Full Name | Java Platform, Standard Edition | Jakarta Enterprise Edition | Java Platform, Micro Edition |
| Main Purpose | General-purpose Java development | Enterprise and server-side applications | Selected embedded and constrained-device applications |
| Primary Environment | Computers, servers, and compatible JVM environments | Compatible enterprise runtimes and application servers | Supported embedded or specialized devices |
| Core Language | Java | Typically Java, using the Java platform and enterprise APIs | Java-based development within supported specifications |
| Key APIs | Collections, I/O, networking, concurrency, JDBC | Servlet, REST, Persistence, CDI, Transactions, Security | APIs defined by the selected Java ME specifications and implementation |
| Resource Requirements | Depends on the application and JVM | Depends on the runtime and enterprise workload | Designed for supported resource-constrained environments |
| Typical Application | Core utilities, desktop programs, and foundational application logic | Enterprise web applications, APIs, and business services | Embedded applications and selected device software |
| Additional Runtime | Compatible Java runtime | Compatible Jakarta EE runtime or server for required specifications | Compatible Java ME runtime or implementation |
| Learning Priority | First for most Java beginners | After learning Java fundamentals and backend concepts | When targeting a device or environment that supports Java ME |
Java SE supplies the standard Java platform foundation. Jakarta EE builds on the Java platform by defining enterprise APIs and services. Java ME addresses a different set of use cases, with specifications and runtimes tailored to supported embedded or constrained environments.
The three platforms should not be treated as interchangeable packages that provide identical APIs. They differ in intended environments, available libraries, runtime requirements, and deployment approaches.
Java Technology Platforms
|
+-------------+-------------+
| | |
Java SE Jakarta EE Java ME
| | |
Core Java and Enterprise Supported embedded
standard APIs APIs and and constrained-device
server services environmentsThis diagram is a conceptual overview. Jakarta EE builds on Java SE, whereas Java ME is a separate platform family with its own specifications and implementation requirements.
Recommended platform: Java SE.
A calculator needs basic language features, arithmetic operations, input handling, and console output. Java SE provides all the essential capabilities for this task.
Recommended platform: Java SE with Jakarta EE where appropriate.
The application may require business logic, database persistence, authentication, transactions, and REST APIs. Java SE provides the core language, while Jakarta EE can provide standardized enterprise services when a compatible runtime is used.
Recommended platform: Jakarta EE or another suitable Java backend framework.
Jakarta EE provides specifications for REST services, dependency injection, persistence, validation, and security. The appropriate choice depends on the team's requirements and preferred runtime.
Recommended platform: Java ME, if supported by the target device.
Java ME may be suitable when the device vendor provides a compatible runtime and the application fits the available specifications and hardware constraints.
Recommended platform: Java SE.
Beginners should learn Java syntax, object-oriented programming, collections, exception handling, and basic database connectivity before moving into enterprise or device-specific development.
| Platform | Recommended Prerequisites | Suggested Learning Path |
|---|---|---|
| Java SE | Basic computer skills and logical thinking | Syntax, control flow, OOP, arrays, collections, exceptions, files, and JDBC |
| Jakarta EE | Core Java, OOP, HTTP basics, SQL, and introductory web development | Servlets, REST APIs, CDI, persistence, validation, security, and transactions |
| Java ME | Java fundamentals and knowledge of the target device | Supported specifications, device APIs, constrained-resource design, testing, and deployment |
javax.*, while newer Jakarta EE APIs commonly use jakarta.*.Create a Student Management console application that stores student names and marks, calculates an average, and displays the results. Use classes, collections, and exception handling.
Create a simple REST endpoint that returns a greeting or a list of products. Deploy it to a compatible Jakarta EE runtime and test the endpoint using a browser or an API client.
Design a small product-management application and identify where Jakarta Persistence, validation, and transaction management could be useful.
Choose a specific embedded device or product and investigate whether it supports Java ME. Document its runtime, supported specifications, memory requirements, and deployment process.
For each project below, select a suitable platform and explain your reasoning:
Answer: Java editions and platform families provide technologies for different application requirements. Java SE supports general-purpose Java development, Jakarta EE supports enterprise applications, and Java ME addresses selected embedded and constrained-device environments.
Answer: Java SE is Java Platform, Standard Edition. It provides the core Java language, standard APIs, runtime foundation, and development tools used to create general-purpose applications.
Answer: Jakarta EE is a collection of enterprise Java specifications and APIs used to develop web applications, REST services, and enterprise systems. It builds on the Java platform and relies on compatible implementations for its enterprise services.
Answer: Java ME is Java Platform, Micro Edition, a family of technologies designed for supported embedded and resource-constrained environments.
Answer: Jakarta EE is the successor to Java EE under the Eclipse Foundation. Modern Jakarta EE versions use the jakarta.* namespace for APIs that underwent the namespace transition, while older Java EE versions and Jakarta EE 8 use many javax.* enterprise package names.
Answer: Strong Java SE knowledge is highly recommended because Jakarta EE applications use Java language features and standard APIs. Understanding OOP, collections, exceptions, and database basics makes enterprise development easier.
Answer: They can run on compatible implementations that support the specifications and versions required by the application. A server that lacks a required specification or uses an incompatible version may not be suitable.
Answer: Java SE is the best starting point for most beginners because it teaches the core language and programming concepts used across the Java ecosystem.
Answer: Java ME is not the standard platform for modern Android development. Android applications use Android APIs and the Android runtime environment, with Kotlin and Java commonly used as programming languages.
Answer: Some ordinary Java language code and compatible libraries may be reusable, but platform-specific APIs, runtime capabilities, dependencies, and deployment requirements differ. Code must be checked and tested against the target platform.
jakarta.* namespace.Understanding Java SE, Jakarta EE, and Java ME helps developers select the right technologies for different software development requirements. Java SE provides the foundation for general-purpose programming, Jakarta EE extends Java technology with standardized enterprise services, and Java ME supports specific embedded and constrained-device environments.
For beginners, learning Core Java through Java SE is the recommended first step. After mastering the fundamentals, learners can explore Jakarta EE for enterprise development or Java ME when working with a device that supports its specifications.
Strengthen your Java fundamentals before progressing to enterprise development or specialized Java platforms. Explore the course information and demo registration options below.
Practice Java programs, understand platform differences, and build small projects to develop a strong foundation for future Java development work.
